projects / ostree.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ca0f02a) | patch
sysroot: Sort returned boot loader configs
authorColin Walters <walters@verbum.org>
Tue, 26 May 2015 22:46:47 +0000 (18:46 -0400)
committerColin Walters <walters@verbum.org>
Thu, 28 May 2015 18:21:30 +0000 (14:21 -0400)
commit3300ee6259d191199f96b5f4e04ccfded3d11b86
tree846eb101134831fd633f3d5fcc5cc15819f3733ftree | snapshot
parentca0f02a54bd9842877b03af01dfd58c139741792commit | diff
sysroot: Sort returned boot loader configs

I haven't done a full dig through the history, but it seems quite
possible right now we've been relying on inode enumeration
order for generating bootloader configuration.

Most of the time, newer inodes (i.e. later written files) will win.
But that's obviously not reliable.

Fix this by sorting the returned configuration internally.
src/libostree/ostree-sysroot.c diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.